Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bad2513a98f18a279509b34bf272cad9d5fcffadb8573bd01f079ddc07c9c2b

Tx prefix hash: 48885492276c41a78ecb15fef9e597af2e3bbb90d0d4c901437c0590601c2354
Tx public key: 6165df1ae3ab365dda6809b89215a34a2628cdbc14f31311f3e64a91f1d46515
Timestamp: 1697011632 Timestamp [UCT]: 2023-10-11 08:07:12 Age [y:d:h:m:s]: 01:184:16:49:00
Block: 867175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393038 RingCT/type: yes/0
Extra: 016165df1ae3ab365dda6809b89215a34a2628cdbc14f31311f3e64a91f1d46515021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.821654570000 dcy

stealth address amount amount idx
00: c0d0ca575f42f49d0eb0959015bae5b41704e451debaccd33154f454af80a2ba 0.821654570000 1321833 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": 867185, "vin": [ { "gen": { "height": 867175 } } ], "vout": [ { "amount": 821654570, "target": { "key": "c0d0ca575f42f49d0eb0959015bae5b41704e451debaccd33154f454af80a2ba" } } ], "extra": [ 1, 97, 101, 223, 26, 227, 171, 54, 93, 218, 104, 9, 184, 146, 21, 163, 74, 38, 40, 205, 188, 20, 243, 19, 17, 243, 230, 74, 145, 241, 212, 101, 21, 2, 17, 0, 0, 0, 5, 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