Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d3c4827f5a1cd670c2afaa3d37c9b68a768febaf0eb3a8c6e3221c0d77bfdcc

Tx prefix hash: 93b531c0032f28f1b65e518e2a68ac7cdaa805cb48457ef419827877ef7575d1
Tx public key: b27f98147bb74805f64326bfdf11a9c984a8de8be175eb84f8575957941e27b5
Timestamp: 1726446625 Timestamp [UCT]: 2024-09-16 00:30:25 Age [y:d:h:m:s]: 00:195:11:15:40
Block: 1111004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139513 RingCT/type: yes/0
Extra: 01b27f98147bb74805f64326bfdf11a9c984a8de8be175eb84f8575957941e27b502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c1ff7706373744a26a2fced17c25170e7da434dc08901747bcd0dc3e3838f9d4 0.600000000000 1589809 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": 1111014, "vin": [ { "gen": { "height": 1111004 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c1ff7706373744a26a2fced17c25170e7da434dc08901747bcd0dc3e3838f9d4" } } ], "extra": [ 1, 178, 127, 152, 20, 123, 183, 72, 5, 246, 67, 38, 191, 223, 17, 169, 201, 132, 168, 222, 139, 225, 117, 235, 132, 248, 87, 89, 87, 148, 30, 39, 181, 2, 17, 0, 0, 0, 5, 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