Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0f676f88b8dfd13f1e58c1091c77ce0aba7ccd18eadf15ba9813e068628ed3c

Tx prefix hash: 086c8cb39857eec751dc73bfa6c1b14dcead3a9463f9701f43ae825218985753
Tx public key: c4f154625cc3bfb94c8f93d77a8f7fee347b1404c05ffb08d869cc4538128a47
Timestamp: 1716889059 Timestamp [UCT]: 2024-05-28 09:37:39 Age [y:d:h:m:s]: 00:272:20:48:28
Block: 1031781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194965 RingCT/type: yes/0
Extra: 01c4f154625cc3bfb94c8f93d77a8f7fee347b1404c05ffb08d869cc4538128a470211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 135b0fa03fe1c692561e9ef3f684ccc94a8c413762917bf8dd0b40829169f2e9 0.600000000000 1500230 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": 1031791, "vin": [ { "gen": { "height": 1031781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "135b0fa03fe1c692561e9ef3f684ccc94a8c413762917bf8dd0b40829169f2e9" } } ], "extra": [ 1, 196, 241, 84, 98, 92, 195, 191, 185, 76, 143, 147, 215, 122, 143, 127, 238, 52, 123, 20, 4, 192, 95, 251, 8, 216, 105, 204, 69, 56, 18, 138, 71, 2, 17, 0, 0, 0, 4, 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