Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f82ffcce2b0620ac66bf9e616902274e9638bd1dbd4fd09e116afb79b8af20c

Tx prefix hash: bf2298cd5cb993e258f4b4f5cd77ea68198c1dd12008ce5dd10ce0aa11c24a11
Tx public key: 56d14250569eecf3e2fd7d8a5e440274dfaa55c6efa61f6a94dce65c30abd91c
Timestamp: 1736248030 Timestamp [UCT]: 2025-01-07 11:07:10 Age [y:d:h:m:s]: 00:149:06:49:33
Block: 1192121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106533 RingCT/type: yes/0
Extra: 0156d14250569eecf3e2fd7d8a5e440274dfaa55c6efa61f6a94dce65c30abd91c021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33c80ce8a70cc680cefd44ceabcf52d78bf445c77a7bff4fa5185a6f31dbeb95 0.600000000000 1678668 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": 1192131, "vin": [ { "gen": { "height": 1192121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33c80ce8a70cc680cefd44ceabcf52d78bf445c77a7bff4fa5185a6f31dbeb95" } } ], "extra": [ 1, 86, 209, 66, 80, 86, 158, 236, 243, 226, 253, 125, 138, 94, 68, 2, 116, 223, 170, 85, 198, 239, 166, 31, 106, 148, 220, 230, 92, 48, 171, 217, 28, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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