Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a30d71fc3912a470903ad73bae5d0424fd399fe6942f75ff05a3f6d2e8dcc016

Tx prefix hash: bcb387e998f373296ff7f5ecc8863f590cecb4246792ca2289c5aef90585d60b
Tx public key: 17726a8df5ee04c4d000852cfc37d1934ce5ecf6273e3fe4a591b59be3f066d5
Timestamp: 1711849496 Timestamp [UCT]: 2024-03-31 01:44:56 Age [y:d:h:m:s]: 01:029:21:24:34
Block: 990001 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282323 RingCT/type: yes/0
Extra: 0117726a8df5ee04c4d000852cfc37d1934ce5ecf6273e3fe4a591b59be3f066d50211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f051ce13ebcfb6c9d949a9fcd57ee12e696cfe6686b2d57e9593e101ad74167 0.600000000000 1450319 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": 990011, "vin": [ { "gen": { "height": 990001 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f051ce13ebcfb6c9d949a9fcd57ee12e696cfe6686b2d57e9593e101ad74167" } } ], "extra": [ 1, 23, 114, 106, 141, 245, 238, 4, 196, 208, 0, 133, 44, 252, 55, 209, 147, 76, 229, 236, 246, 39, 62, 63, 228, 165, 145, 181, 155, 227, 240, 102, 213, 2, 17, 0, 0, 0, 6, 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