Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c723be1abaea1442a29c9fcaf6e26b3ce84201541e22c40dfc6d686eb957ddb

Tx prefix hash: b2490fb73cd495d25a466945a5d4c3919cbabfb9a19fcb40beadfa963d196b1b
Tx public key: d6202ce38bd0c1d1bbcaaaf9b2c5b915f4c07293c133e7e8bf6bae89cc413ee8
Timestamp: 1715873842 Timestamp [UCT]: 2024-05-16 15:37:22 Age [y:d:h:m:s]: 00:361:12:04:32
Block: 1023347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258407 RingCT/type: yes/0
Extra: 01d6202ce38bd0c1d1bbcaaaf9b2c5b915f4c07293c133e7e8bf6bae89cc413ee80211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a74cb76eaaa8ab2dc2c71a4aeabca1cb2354f0eb7c95d41cac017ddbe5fa7b0 0.600000000000 1488260 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": 1023357, "vin": [ { "gen": { "height": 1023347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a74cb76eaaa8ab2dc2c71a4aeabca1cb2354f0eb7c95d41cac017ddbe5fa7b0" } } ], "extra": [ 1, 214, 32, 44, 227, 139, 208, 193, 209, 187, 202, 170, 249, 178, 197, 185, 21, 244, 192, 114, 147, 193, 51, 231, 232, 191, 107, 174, 137, 204, 65, 62, 232, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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