Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfc6b3dd71a0a245e6bc2de52676c29e3be22c8ef9dbea848d8d7ac608457654

Tx prefix hash: 1a54dbd5469cc391eebbed32faec0cefacbc04f8c860c6320efadd301e5e8d6c
Tx public key: 27ece9906e917ac4a8296a7d6610b1adf6cac3958baa266b19a09627e291e98f
Timestamp: 1704482599 Timestamp [UCT]: 2024-01-05 19:23:19 Age [y:d:h:m:s]: 01:353:01:29:17
Block: 928898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 511211 RingCT/type: yes/0
Extra: 0127ece9906e917ac4a8296a7d6610b1adf6cac3958baa266b19a09627e291e98f02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2616703da77c780bdb66f6a483ca12aa6338fb8bf45ca2e0e921656744bad79b 0.600000000000 1386764 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": 928908, "vin": [ { "gen": { "height": 928898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2616703da77c780bdb66f6a483ca12aa6338fb8bf45ca2e0e921656744bad79b" } } ], "extra": [ 1, 39, 236, 233, 144, 110, 145, 122, 196, 168, 41, 106, 125, 102, 16, 177, 173, 246, 202, 195, 149, 139, 170, 38, 107, 25, 160, 150, 39, 226, 145, 233, 143, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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