Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1214a915fcaf5653120ae294824a371036b3c2f24967f8d45fb02666a9e10d98

Tx prefix hash: 39d3d42f2ed8f62bccbd522a37c2e881ad6f94eb1040987f5e185eb2981c650e
Tx public key: ab75cf796c9a3fe9c1311b2037275a5947c992e5f9d4cb406aa71f99b26b6e58
Timestamp: 1674665266 Timestamp [UCT]: 2023-01-25 16:47:46 Age [y:d:h:m:s]: 02:111:18:24:33
Block: 682582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 601537 RingCT/type: yes/0
Extra: 01ab75cf796c9a3fe9c1311b2037275a5947c992e5f9d4cb406aa71f99b26b6e580211000000015029cbac000000000000000000

1 output(s) for total of 3.359869579000 dcy

stealth address amount amount idx
00: a21269cdebd338c7a25c5254b863f340d5010f5189935ce7da00359143a436a0 3.359869579000 1124713 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": 682592, "vin": [ { "gen": { "height": 682582 } } ], "vout": [ { "amount": 3359869579, "target": { "key": "a21269cdebd338c7a25c5254b863f340d5010f5189935ce7da00359143a436a0" } } ], "extra": [ 1, 171, 117, 207, 121, 108, 154, 63, 233, 193, 49, 27, 32, 55, 39, 90, 89, 71, 201, 146, 229, 249, 212, 203, 64, 106, 167, 31, 153, 178, 107, 110, 88, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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