Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c5216df7320795c37e0aea6deae8b1f1237eda40c22c20a9014dce23c4c79b3

Tx prefix hash: 377c561056eef9c6b6977c8c0f22b70a6d66fe88f485e4d40cb5b2c9ef034f80
Tx public key: 24e9ecb381fa8bcc841d3120d18cf0633c16096f86cb0517282c47e8666056fa
Timestamp: 1721557353 Timestamp [UCT]: 2024-07-21 10:22:33 Age [y:d:h:m:s]: 00:257:23:19:31
Block: 1070458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184300 RingCT/type: yes/0
Extra: 0124e9ecb381fa8bcc841d3120d18cf0633c16096f86cb0517282c47e8666056fa02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e075cc43d624960ba2ff966eadbcca1c31ee0ed45ab3d2f1e5aa946dd5e4d02 0.600000000000 1542299 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": 1070468, "vin": [ { "gen": { "height": 1070458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e075cc43d624960ba2ff966eadbcca1c31ee0ed45ab3d2f1e5aa946dd5e4d02" } } ], "extra": [ 1, 36, 233, 236, 179, 129, 250, 139, 204, 132, 29, 49, 32, 209, 140, 240, 99, 60, 22, 9, 111, 134, 203, 5, 23, 40, 44, 71, 232, 102, 96, 86, 250, 2, 17, 0, 0, 0, 6, 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