Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 5abc6642924a338b9a1faef37ad4b72353c5f9657f6f9c539ec92fd7438688a7

Tx prefix hash: 5b6af96331cfc1b0145666511611162ea5784558030f6564ad6cfe952596d831
Tx public key: f3953dc3c1ce67795b3bc27f9a3f6e40c07fa2976af64b5cb0615c4708386bd4
Timestamp: 1574738591 Timestamp [UCT]: 2019-11-26 03:23:11 Age [y:d:h:m:s]: 04:347:02:07:37
Block: 17621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129969 RingCT/type: yes/0
Extra: 01f3953dc3c1ce67795b3bc27f9a3f6e40c07fa2976af64b5cb0615c4708386bd4021100000028b63f0b49000000000000000000

1 output(s) for total of 536.556169000000 dcy

stealth address amount amount idx
00: 25b7fc9419fa9ff610a8813e00d90aa002f4ccb909b5b342b1ab4aa1bd689066 536.556169000000 25877 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 17631, "vin": [ { "gen": { "height": 17621 } } ], "vout": [ { "amount": 536556169000, "target": { "key": "25b7fc9419fa9ff610a8813e00d90aa002f4ccb909b5b342b1ab4aa1bd689066" } } ], "extra": [ 1, 243, 149, 61, 195, 193, 206, 103, 121, 91, 59, 194, 127, 154, 63, 110, 64, 192, 127, 162, 151, 106, 246, 75, 92, 176, 97, 92, 71, 8, 56, 107, 212, 2, 17, 0, 0, 0, 40, 182, 63, 11, 73, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8