Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 057e3779d8c0782041601a7b822139f8d3fc097514ce0c27b674166cfe370aa7

Tx prefix hash: 8c4cd2c9697c6b8268e6bcb262f243882b96931e4b3617cd5cc032a664356ce1
Tx public key: d0974c4465f7b6754c0f29c4af33d08a7405dee921f0ec4e4313ac8a7340abf2
Timestamp: 1745273342 Timestamp [UCT]: 2025-04-21 22:09:02 Age [y:d:h:m:s]: 00:202:21:36:40
Block: 1266570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142728 RingCT/type: yes/0
Extra: 01d0974c4465f7b6754c0f29c4af33d08a7405dee921f0ec4e4313ac8a7340abf202110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dbd0cadc1bc5e71a9164775622ed0b0587a0363ba992536eb382e0c0473ea01b 0.600000000000 1753791 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": 1266580, "vin": [ { "gen": { "height": 1266570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dbd0cadc1bc5e71a9164775622ed0b0587a0363ba992536eb382e0c0473ea01b" } } ], "extra": [ 1, 208, 151, 76, 68, 101, 247, 182, 117, 76, 15, 41, 196, 175, 51, 208, 138, 116, 5, 222, 233, 33, 240, 236, 78, 67, 19, 172, 138, 115, 64, 171, 242, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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