Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0255889f586b4a13e94d8c003297fd1fca3298ac24bbe9883c4bf2e7bbfc17e0

Tx prefix hash: 7dd106081b1f4a367b86aba7891a50b26caab233d160109c1f6a4b141b24b0ec
Tx public key: 1f8f0bbd19beec38daea6acd36ef97415eea6d1e2b033e2b42713e34060c85d0
Timestamp: 1705561479 Timestamp [UCT]: 2024-01-18 07:04:39 Age [y:d:h:m:s]: 01:080:05:04:59
Block: 937826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318428 RingCT/type: yes/0
Extra: 011f8f0bbd19beec38daea6acd36ef97415eea6d1e2b033e2b42713e34060c85d00211000000107a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91770b538bd982cc03cead8186e40c624e4373716adaa13b571c5ea5d965ec1e 0.600000000000 1395890 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": 937836, "vin": [ { "gen": { "height": 937826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91770b538bd982cc03cead8186e40c624e4373716adaa13b571c5ea5d965ec1e" } } ], "extra": [ 1, 31, 143, 11, 189, 25, 190, 236, 56, 218, 234, 106, 205, 54, 239, 151, 65, 94, 234, 109, 30, 43, 3, 62, 43, 66, 113, 62, 52, 6, 12, 133, 208, 2, 17, 0, 0, 0, 16, 122, 156, 244, 199, 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