Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64d345700f6e0215a53604542dcc7dc988a71931cba387392bb48fcad3fa368f

Tx prefix hash: 83c2af2dcc5f6cdc99638bb21d57d82219df0fa4df62bc9904d03c8505c20be2
Tx public key: 55aa1a6671e6afb9f1327758d736c0925e28e844f269bd677cbf3fbc424f9d5e
Timestamp: 1686987104 Timestamp [UCT]: 2023-06-17 07:31:44 Age [y:d:h:m:s]: 01:348:10:02:23
Block: 784117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510229 RingCT/type: yes/0
Extra: 0155aa1a6671e6afb9f1327758d736c0925e28e844f269bd677cbf3fbc424f9d5e021100000009e6d27f9c000000000000000000

1 output(s) for total of 1.548442310000 dcy

stealth address amount amount idx
00: b98ef9d7124fe93844a36f467e6cf61c1a1fb279fc967cf70fae0d97a9511d7f 1.548442310000 1233996 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": 784127, "vin": [ { "gen": { "height": 784117 } } ], "vout": [ { "amount": 1548442310, "target": { "key": "b98ef9d7124fe93844a36f467e6cf61c1a1fb279fc967cf70fae0d97a9511d7f" } } ], "extra": [ 1, 85, 170, 26, 102, 113, 230, 175, 185, 241, 50, 119, 88, 215, 54, 192, 146, 94, 40, 232, 68, 242, 105, 189, 103, 124, 191, 63, 188, 66, 79, 157, 94, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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