Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3334a4107b26c5c6abccadbade1ed02f9aade2da22eb0a964c998050550665dd

Tx prefix hash: 0bd28a26ef0504e0b5e6da118c3259c19751a3b885de4a7d04a81563cb34e62a
Tx public key: 77b8a10d48f6328a234fe3e516b97ac89e2be5711e386bfc1ac2350f67a9fd31
Timestamp: 1727806675 Timestamp [UCT]: 2024-10-01 18:17:55 Age [y:d:h:m:s]: 00:185:03:26:52
Block: 1122284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 132108 RingCT/type: yes/0
Extra: 0177b8a10d48f6328a234fe3e516b97ac89e2be5711e386bfc1ac2350f67a9fd3102110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fafc9e213dcd6032f786388404ffe3ea1ae7db6dfa4b99f4e16c971e5b48bed 0.600000000000 1604695 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": 1122294, "vin": [ { "gen": { "height": 1122284 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fafc9e213dcd6032f786388404ffe3ea1ae7db6dfa4b99f4e16c971e5b48bed" } } ], "extra": [ 1, 119, 184, 161, 13, 72, 246, 50, 138, 35, 79, 227, 229, 22, 185, 122, 200, 158, 43, 229, 113, 30, 56, 107, 252, 26, 194, 53, 15, 103, 169, 253, 49, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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