Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e441f98e94c39ea582ab7478fabbbcb7a13f67dc081be4c59c6e5c10b309c9a

Tx prefix hash: 033bf1ce9955051b39081441a41f376ae8831f60f81e2f21720c8a4bca95237d
Tx public key: 81c59fd4296589f9b2586e32131922fdee8eeedaa49ce34222af59a7c3f1af5b
Timestamp: 1717111643 Timestamp [UCT]: 2024-05-30 23:27:23 Age [y:d:h:m:s]: 00:177:23:03:35
Block: 1033609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127374 RingCT/type: yes/0
Extra: 0181c59fd4296589f9b2586e32131922fdee8eeedaa49ce34222af59a7c3f1af5b0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36795490d7d356d41d8b3600aca5cb33f2daeb9c03584a811ff92db18704fd18 0.600000000000 1502080 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": 1033619, "vin": [ { "gen": { "height": 1033609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36795490d7d356d41d8b3600aca5cb33f2daeb9c03584a811ff92db18704fd18" } } ], "extra": [ 1, 129, 197, 159, 212, 41, 101, 137, 249, 178, 88, 110, 50, 19, 25, 34, 253, 238, 142, 238, 218, 164, 156, 227, 66, 34, 175, 89, 167, 195, 241, 175, 91, 2, 17, 0, 0, 0, 5, 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