Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ac3099566f23f82eb8dcb5ee421cf6651b9c750d1a19a0ba3ef375f778b798b

Tx prefix hash: e17d0574339a3087008097f373e3a69378ed6155648145e29e4f7e19d4e65ce1
Tx public key: 92be0ae2b682caae48e9e2a90f973571c7ebd4d3c7a372fb0f5911671827945b
Timestamp: 1702677416 Timestamp [UCT]: 2023-12-15 21:56:56 Age [y:d:h:m:s]: 01:035:05:41:18
Block: 913935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286513 RingCT/type: yes/0
Extra: 0192be0ae2b682caae48e9e2a90f973571c7ebd4d3c7a372fb0f5911671827945b02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fd9507f5d7b5168f70243cd734bee85b1aadedcaabbd46a33f638c73132acb3 0.600000000000 1371215 of 15

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": 913945, "vin": [ { "gen": { "height": 913935 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fd9507f5d7b5168f70243cd734bee85b1aadedcaabbd46a33f638c73132acb3" } } ], "extra": [ 1, 146, 190, 10, 226, 182, 130, 202, 174, 72, 233, 226, 169, 15, 151, 53, 113, 199, 235, 212, 211, 199, 163, 114, 251, 15, 89, 17, 103, 24, 39, 148, 91, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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