Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b657b4bd3d8dac2a23b8445573a6dfd4c14edfc0f2debfd753d1be39a0cd201

Tx prefix hash: be52c465c3a26f9b69cdd4f8135839ee3a62f477ee72204f02c1bb2329efffb3
Tx public key: bbffe1da5c428946e44c2d33b37dd76062654bedac0b7ccf84bf9699f37b774e
Timestamp: 1708036125 Timestamp [UCT]: 2024-02-15 22:28:45 Age [y:d:h:m:s]: 01:074:05:13:53
Block: 958359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314107 RingCT/type: yes/0
Extra: 01bbffe1da5c428946e44c2d33b37dd76062654bedac0b7ccf84bf9699f37b774e02110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1491a6bc7cf6d6f4cb7833150e294e4d554cf120f80d395f50f80d4b6c4dee7 0.600000000000 1417718 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": 958369, "vin": [ { "gen": { "height": 958359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1491a6bc7cf6d6f4cb7833150e294e4d554cf120f80d395f50f80d4b6c4dee7" } } ], "extra": [ 1, 187, 255, 225, 218, 92, 66, 137, 70, 228, 76, 45, 51, 179, 125, 215, 96, 98, 101, 75, 237, 172, 11, 124, 207, 132, 191, 150, 153, 243, 123, 119, 78, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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