Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c3b185e401a0f7662684b6ecefb973609c9208af400e63955a3ec17691878a6

Tx prefix hash: f3e2d81307f2d1c6114b263e207647f8ecbfeec277467466a448f2a91523f527
Tx public key: 546e7196b5d30e1f61e12bc1d9e8056b155244d7066a586c3b29f336f62ca23c
Timestamp: 1702331256 Timestamp [UCT]: 2023-12-11 21:47:36 Age [y:d:h:m:s]: 01:118:15:35:13
Block: 911083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345917 RingCT/type: yes/0
Extra: 01546e7196b5d30e1f61e12bc1d9e8056b155244d7066a586c3b29f336f62ca23c02110000000633af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a7c69a481a24e4880bf06d2190062074ff013e35811f418b3e07cbd3d58a651 0.600000000000 1368258 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": 911093, "vin": [ { "gen": { "height": 911083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a7c69a481a24e4880bf06d2190062074ff013e35811f418b3e07cbd3d58a651" } } ], "extra": [ 1, 84, 110, 113, 150, 181, 211, 14, 31, 97, 225, 43, 193, 217, 232, 5, 107, 21, 82, 68, 215, 6, 106, 88, 108, 59, 41, 243, 54, 246, 44, 162, 60, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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