Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84284fbb166a05d52e50798cca1f4de6715307e7117e3fad3b65136f76ae4384

Tx prefix hash: 42cd811e219cdb1b54c59df42bd4b2646ee72d263f65f6e36605b738a6e86161
Tx public key: d7bc4c1b3c4ffb411aa4cac5e9de14f3ce70e1e7488d1ecc0c4f5e1d85ddf4cd
Timestamp: 1724184964 Timestamp [UCT]: 2024-08-20 20:16:04 Age [y:d:h:m:s]: 00:187:02:24:01
Block: 1092260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133545 RingCT/type: yes/0
Extra: 01d7bc4c1b3c4ffb411aa4cac5e9de14f3ce70e1e7488d1ecc0c4f5e1d85ddf4cd02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 265ca9818e2f425b5ada88fd5db712a928153d727ccf78bddedd4de742387af2 0.600000000000 1566969 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": 1092270, "vin": [ { "gen": { "height": 1092260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "265ca9818e2f425b5ada88fd5db712a928153d727ccf78bddedd4de742387af2" } } ], "extra": [ 1, 215, 188, 76, 27, 60, 79, 251, 65, 26, 164, 202, 197, 233, 222, 20, 243, 206, 112, 225, 231, 72, 141, 30, 204, 12, 79, 94, 29, 133, 221, 244, 205, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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