Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53e72215e3737127ca45cd3d4def081886e0950a43236550160b09d1be0e5b66

Tx prefix hash: e8fd9c8e78ef03c63cd9a25b2af1551b8039865aacebf9bed2571ecbc658b5ec
Tx public key: b31df8ba588b4d56b4899cd74bb584a27a6ec24317b86e99456a13f593d133a7
Timestamp: 1698513471 Timestamp [UCT]: 2023-10-28 17:17:51 Age [y:d:h:m:s]: 01:172:12:41:55
Block: 879637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384311 RingCT/type: yes/0
Extra: 01b31df8ba588b4d56b4899cd74bb584a27a6ec24317b86e99456a13f593d133a70211000000014b8f5122000000000000000000

1 output(s) for total of 0.747132240000 dcy

stealth address amount amount idx
00: 4794f3edd973d1272d4ad6d0cb9c713a8f400a1ce5619746612fbb22f68498cb 0.747132240000 1335171 of 0

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": 879647, "vin": [ { "gen": { "height": 879637 } } ], "vout": [ { "amount": 747132240, "target": { "key": "4794f3edd973d1272d4ad6d0cb9c713a8f400a1ce5619746612fbb22f68498cb" } } ], "extra": [ 1, 179, 29, 248, 186, 88, 139, 77, 86, 180, 137, 156, 215, 75, 181, 132, 162, 122, 110, 194, 67, 23, 184, 110, 153, 69, 106, 19, 245, 147, 209, 51, 167, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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