Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abc1bb17a2bca1a7c021cb8966888aaa3a5430a330769ddbc7d981c39613453d

Tx prefix hash: a688b32dd0d96e6f24faa3247065a190015c445e7ab3c03fe68639f46f0fc3c0
Tx public key: 0fde078cc6095560a7821d96f1d4af8ae17cbff45fe4017c7a72b99c861211d6
Timestamp: 1711244794 Timestamp [UCT]: 2024-03-24 01:46:34 Age [y:d:h:m:s]: 01:078:20:33:57
Block: 984988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317368 RingCT/type: yes/0
Extra: 010fde078cc6095560a7821d96f1d4af8ae17cbff45fe4017c7a72b99c861211d60211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3b9496ebda9508ec7b4be8fc16d0f298c62cef9e4eba1438edd172df558cc7a 0.600000000000 1445193 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": 984998, "vin": [ { "gen": { "height": 984988 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3b9496ebda9508ec7b4be8fc16d0f298c62cef9e4eba1438edd172df558cc7a" } } ], "extra": [ 1, 15, 222, 7, 140, 198, 9, 85, 96, 167, 130, 29, 150, 241, 212, 175, 138, 225, 124, 191, 244, 95, 228, 1, 124, 122, 114, 185, 156, 134, 18, 17, 214, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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