Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dc46f035e117c4ff65167b5dfeb61d8b46fcc4499b22780ffcdc7bbf2365df4

Tx prefix hash: e0f5f7eca9c0518d4e92ddfc02fa4fddadb457c15e01e86318833640142a940a
Tx public key: 7fb3c788b0bc889d57911e207b20be1e153d86ac1b88e7ec63a18582b7445af2
Timestamp: 1709332637 Timestamp [UCT]: 2024-03-01 22:37:17 Age [y:d:h:m:s]: 01:109:17:24:22
Block: 969124 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 339344 RingCT/type: yes/0
Extra: 017fb3c788b0bc889d57911e207b20be1e153d86ac1b88e7ec63a18582b7445af20211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa08a605300318fac5dff8180ed5bacd9b8c51f501dfefbe1bc2fd4ae58f7134 0.600000000000 1428951 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": 969134, "vin": [ { "gen": { "height": 969124 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa08a605300318fac5dff8180ed5bacd9b8c51f501dfefbe1bc2fd4ae58f7134" } } ], "extra": [ 1, 127, 179, 199, 136, 176, 188, 136, 157, 87, 145, 30, 32, 123, 32, 190, 30, 21, 61, 134, 172, 27, 136, 231, 236, 99, 161, 133, 130, 183, 68, 90, 242, 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