Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a80ba4bdc7a2698e6b4b84fc078a2ca344584ddcfe48cac4abdae5dfcdea8695

Tx prefix hash: acd97f0aada666888d6cdd3474fe907729b4a99b3542d33faa40eb417dd4908d
Tx public key: e2785cbae6bedff5f6cdb0e50784b3c9fdb4abf2e273f306bd6698a3be8e5791
Timestamp: 1706339724 Timestamp [UCT]: 2024-01-27 07:15:24 Age [y:d:h:m:s]: 01:072:20:23:53
Block: 944275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313155 RingCT/type: yes/0
Extra: 01e2785cbae6bedff5f6cdb0e50784b3c9fdb4abf2e273f306bd6698a3be8e579102110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b81bcfe27e35d12fc5800a3cf3a38968481aa613764480e7ea03edf2df20ee31 0.600000000000 1402511 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": 944285, "vin": [ { "gen": { "height": 944275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b81bcfe27e35d12fc5800a3cf3a38968481aa613764480e7ea03edf2df20ee31" } } ], "extra": [ 1, 226, 120, 92, 186, 230, 190, 223, 245, 246, 205, 176, 229, 7, 132, 179, 201, 253, 180, 171, 242, 226, 115, 243, 6, 189, 102, 152, 163, 190, 142, 87, 145, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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