Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c49feb52efad701ed7976d2d6087be8fae6f2dd4c87cbbe8e943ca888bb6dfa3

Tx prefix hash: f73eac620a731240fec50710590ef6cbc83b905ec53da39ecbddc3ab810756b4
Tx public key: ac66daebae96c74eb5abfce3981faa8a3b85bf816db2c1acc7fc70716ed3e4ae
Timestamp: 1728518433 Timestamp [UCT]: 2024-10-10 00:00:33 Age [y:d:h:m:s]: 01:104:06:33:30
Block: 1128173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332855 RingCT/type: yes/0
Extra: 01ac66daebae96c74eb5abfce3981faa8a3b85bf816db2c1acc7fc70716ed3e4ae02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e10be1472d9dbc4829a3c43490a988a9b2b455de4ea7472e29ae90f3b91cee6 0.600000000000 1610990 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": 1128183, "vin": [ { "gen": { "height": 1128173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e10be1472d9dbc4829a3c43490a988a9b2b455de4ea7472e29ae90f3b91cee6" } } ], "extra": [ 1, 172, 102, 218, 235, 174, 150, 199, 78, 181, 171, 252, 227, 152, 31, 170, 138, 59, 133, 191, 129, 109, 178, 193, 172, 199, 252, 112, 113, 110, 211, 228, 174, 2, 17, 0, 0, 0, 1, 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