Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0ee200df68ca38850b9c745b28f1a2dab614d070499448c3c03486c36aa026b

Tx prefix hash: d64166c2e577e67ed8cc0f7ee43476072680fc86761e67275bbdbb30e141d701
Tx public key: f2dcf8103670e185516c19bde93995f86e019e50c2d52a822e7da8642724fdc8
Timestamp: 1700666373 Timestamp [UCT]: 2023-11-22 15:19:33 Age [y:d:h:m:s]: 01:138:23:33:33
Block: 897269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360501 RingCT/type: yes/0
Extra: 01f2dcf8103670e185516c19bde93995f86e019e50c2d52a822e7da8642724fdc8021100000001faf35c9c000000000000000000

1 output(s) for total of 0.653093432000 dcy

stealth address amount amount idx
00: 24783de3b20fe0583ef0bc463b3c3b2f66afa3f67dafd25664fb7de027b98a9a 0.653093432000 1353638 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": 897279, "vin": [ { "gen": { "height": 897269 } } ], "vout": [ { "amount": 653093432, "target": { "key": "24783de3b20fe0583ef0bc463b3c3b2f66afa3f67dafd25664fb7de027b98a9a" } } ], "extra": [ 1, 242, 220, 248, 16, 54, 112, 225, 133, 81, 108, 25, 189, 233, 57, 149, 248, 110, 1, 158, 80, 194, 213, 42, 130, 46, 125, 168, 100, 39, 36, 253, 200, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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