Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 610da4d38335b234ed3a00e6798b376bcdf657c6c4395e497223f1a6c7642b98

Tx prefix hash: 9d54dee0fd7a1a10a65ea399074140a9c2ee3429e724bc448bf09fbe8b0146e9
Tx public key: 37c697c91eb1db7ad5a64a1cce5997fb588bd448345ed0da256ec4a93fcb9a6d
Timestamp: 1681565647 Timestamp [UCT]: 2023-04-15 13:34:07 Age [y:d:h:m:s]: 01:320:20:00:29
Block: 739157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490550 RingCT/type: yes/0
Extra: 0137c697c91eb1db7ad5a64a1cce5997fb588bd448345ed0da256ec4a93fcb9a6d0211000000035029cbac000000000000000000

1 output(s) for total of 2.182057745000 dcy

stealth address amount amount idx
00: 3879863867804a2a7695a58f8f6e0e3ce922c7d7cb0884f0843e86b5a418b29f 2.182057745000 1185978 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": 739167, "vin": [ { "gen": { "height": 739157 } } ], "vout": [ { "amount": 2182057745, "target": { "key": "3879863867804a2a7695a58f8f6e0e3ce922c7d7cb0884f0843e86b5a418b29f" } } ], "extra": [ 1, 55, 198, 151, 201, 30, 177, 219, 122, 213, 166, 74, 28, 206, 89, 151, 251, 88, 139, 212, 72, 52, 94, 208, 218, 37, 110, 196, 169, 63, 203, 154, 109, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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