Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52b5263cd0041e95559af9d3ebe04e723ab630f375f4d049cb57a89d55e72e3e

Tx prefix hash: 88c2e632e9bca5341ad4f3ffc75ab2ebc712f89908546e8ef67dfe7666b8bc7d
Tx public key: d474e8c34ad86987afc30d26a5f7a8d377464d99ce24532e6ec4110e325a97f1
Timestamp: 1737681504 Timestamp [UCT]: 2025-01-24 01:18:24 Age [y:d:h:m:s]: 00:048:02:19:13
Block: 1203951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34189 RingCT/type: yes/0
Extra: 01d474e8c34ad86987afc30d26a5f7a8d377464d99ce24532e6ec4110e325a97f1021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c45b968e83a64ee5d83d80c52e11bef0d740129d5b322ec640e4f4686f4651b0 0.600000000000 1690632 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": 1203961, "vin": [ { "gen": { "height": 1203951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c45b968e83a64ee5d83d80c52e11bef0d740129d5b322ec640e4f4686f4651b0" } } ], "extra": [ 1, 212, 116, 232, 195, 74, 216, 105, 135, 175, 195, 13, 38, 165, 247, 168, 211, 119, 70, 77, 153, 206, 36, 83, 46, 110, 196, 17, 14, 50, 90, 151, 241, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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