Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59342d57825a0fea4d359684f220667f25c5fed08b698d66de7f100e3b07058f

Tx prefix hash: 6e83f6eaabc76b32ac90a55d3c1c5fa961dacfd095dd4a36993ad98652be60bd
Tx public key: 6a5624960e6cc357ce145bc5d7c58ba3e82f25717b5ddb20f38c5233a8e77cd5
Timestamp: 1700202933 Timestamp [UCT]: 2023-11-17 06:35:33 Age [y:d:h:m:s]: 01:065:19:03:59
Block: 893419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308394 RingCT/type: yes/0
Extra: 016a5624960e6cc357ce145bc5d7c58ba3e82f25717b5ddb20f38c5233a8e77cd502110000000733af99f4000000000000000000

1 output(s) for total of 0.672561449000 dcy

stealth address amount amount idx
00: aa6edb5d72402827b8858a9576c13af81b94cb99146d5419d1c808874f63c9b8 0.672561449000 1349584 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": 893429, "vin": [ { "gen": { "height": 893419 } } ], "vout": [ { "amount": 672561449, "target": { "key": "aa6edb5d72402827b8858a9576c13af81b94cb99146d5419d1c808874f63c9b8" } } ], "extra": [ 1, 106, 86, 36, 150, 14, 108, 195, 87, 206, 20, 91, 197, 215, 197, 139, 163, 232, 47, 37, 113, 123, 93, 219, 32, 243, 140, 82, 51, 168, 231, 124, 213, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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