Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 092d86d7dfe5c7fcf37fa2abdd86d9821159803f452d4d34c42de2e91db2c290

Tx prefix hash: daa145b19fe317a3c4338d286ef7361ea73cc3c14a3ccd1ae96bb48fc24e7b23
Tx public key: dae2bfd7c569e91413e612e5bb31290e73b377184d9c15747bfb13b99a345821
Timestamp: 1708155485 Timestamp [UCT]: 2024-02-17 07:38:05 Age [y:d:h:m:s]: 01:038:06:55:58
Block: 959353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288382 RingCT/type: yes/0
Extra: 01dae2bfd7c569e91413e612e5bb31290e73b377184d9c15747bfb13b99a34582102110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9a0d8f413f6220daeec09b20a9ba1719b18dd6ca5a396d2051323edc1e08bfe2 0.600000000000 1418888 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": 959363, "vin": [ { "gen": { "height": 959353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9a0d8f413f6220daeec09b20a9ba1719b18dd6ca5a396d2051323edc1e08bfe2" } } ], "extra": [ 1, 218, 226, 191, 215, 197, 105, 233, 20, 19, 230, 18, 229, 187, 49, 41, 14, 115, 179, 119, 24, 77, 156, 21, 116, 123, 251, 19, 185, 154, 52, 88, 33, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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