Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 335e6a80e735c920b5968e507b788721228477bf9ae9f18f2db7a2ab8115dfd7

Tx prefix hash: fe5ab8d12435460ade376e09ffe2d2e808d67bcc6ef30b795de5df5836429226
Tx public key: a7346eb1d65e0da8d34f464e9bf433776c2faef128279dc14d550f36b9853a60
Timestamp: 1714573447 Timestamp [UCT]: 2024-05-01 14:24:07 Age [y:d:h:m:s]: 01:026:04:08:13
Block: 1012573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279650 RingCT/type: yes/0
Extra: 01a7346eb1d65e0da8d34f464e9bf433776c2faef128279dc14d550f36b9853a600211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6abdf8b8e29c2ec4e92e2c224da719b15c71e7c167d4fb7eba96a7ac405566e 0.600000000000 1475141 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": 1012583, "vin": [ { "gen": { "height": 1012573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6abdf8b8e29c2ec4e92e2c224da719b15c71e7c167d4fb7eba96a7ac405566e" } } ], "extra": [ 1, 167, 52, 110, 177, 214, 94, 13, 168, 211, 79, 70, 78, 155, 244, 51, 119, 108, 47, 174, 241, 40, 39, 157, 193, 77, 85, 15, 54, 185, 133, 58, 96, 2, 17, 0, 0, 0, 2, 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