Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86a4b0078dc135d59377de30d9629d24a06ab8e6d4bb9560fe05cf6e4439cc52

Tx prefix hash: 0f166ca479eb85c3d4a4d65a2422e3a0dda44763755392ef71ba76eb90261493
Tx public key: 3b96655a2b7dc1bd728af2753fdbc624c8c57aa13c31ef70a139e7d0b3680c3c
Timestamp: 1709788707 Timestamp [UCT]: 2024-03-07 05:18:27 Age [y:d:h:m:s]: 01:065:14:00:05
Block: 972906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307886 RingCT/type: yes/0
Extra: 013b96655a2b7dc1bd728af2753fdbc624c8c57aa13c31ef70a139e7d0b3680c3c0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eec8f31734439347091b9b65f2f15e7c07b552e1d69b20a51989117e23bdddac 0.600000000000 1432825 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": 972916, "vin": [ { "gen": { "height": 972906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eec8f31734439347091b9b65f2f15e7c07b552e1d69b20a51989117e23bdddac" } } ], "extra": [ 1, 59, 150, 101, 90, 43, 125, 193, 189, 114, 138, 242, 117, 63, 219, 198, 36, 200, 197, 122, 161, 60, 49, 239, 112, 161, 57, 231, 208, 179, 104, 12, 60, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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