Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f95ef98986ef9cf6799ef23fb0c4f892b1bbee473ddb1a24c485e54eb3cb013a

Tx prefix hash: fba6a2d8dd3d947dab3fc23a8787b48c66fc686ec12e421ad75ccfd06c24bb3f
Tx public key: 5f95b1434fb1a7cdf1da3bdc298503265a51b90aed76edc3bb8e70884cab64df
Timestamp: 1711298487 Timestamp [UCT]: 2024-03-24 16:41:27 Age [y:d:h:m:s]: 01:049:22:15:31
Block: 985432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296664 RingCT/type: yes/0
Extra: 015f95b1434fb1a7cdf1da3bdc298503265a51b90aed76edc3bb8e70884cab64df0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54b218a386ec210a69e0919701afee880b99baf137b2df380577dc63be81c043 0.600000000000 1445643 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": 985442, "vin": [ { "gen": { "height": 985432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54b218a386ec210a69e0919701afee880b99baf137b2df380577dc63be81c043" } } ], "extra": [ 1, 95, 149, 177, 67, 79, 177, 167, 205, 241, 218, 59, 220, 41, 133, 3, 38, 90, 81, 185, 10, 237, 118, 237, 195, 187, 142, 112, 136, 76, 171, 100, 223, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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