Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1055d1be8494180dee36092fbf0184a698befbfe11b23810cb6a486bdeba6ef

Tx prefix hash: 05060f92824a7fe12930b42c6bc765f3dfee5ae0d4ae1451a1d4a2d21d3906eb
Tx public key: 7e08c18402ba775604d482e80e2d6f21e64d48baa591902f30054056353c4773
Timestamp: 1647689721 Timestamp [UCT]: 2022-03-19 11:35:21 Age [y:d:h:m:s]: 02:279:03:27:56
Block: 461785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 719031 RingCT/type: yes/0
Extra: 017e08c18402ba775604d482e80e2d6f21e64d48baa591902f30054056353c4773021100000007bf7ee4e7000000000000000000

1 output(s) for total of 18.109850303000 dcy

stealth address amount amount idx
00: ff7ccd023d163de102527e977b619ab47c1ee3c82c495b18ae7025f3d2d4c183 18.109850303000 879102 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": 461795, "vin": [ { "gen": { "height": 461785 } } ], "vout": [ { "amount": 18109850303, "target": { "key": "ff7ccd023d163de102527e977b619ab47c1ee3c82c495b18ae7025f3d2d4c183" } } ], "extra": [ 1, 126, 8, 193, 132, 2, 186, 119, 86, 4, 212, 130, 232, 14, 45, 111, 33, 230, 77, 72, 186, 165, 145, 144, 47, 48, 5, 64, 86, 53, 60, 71, 115, 2, 17, 0, 0, 0, 7, 191, 126, 228, 231, 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