Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ce0db7ed9620aaaca6c128437301c6edd080088c21fa46f35bbd25e588a4309

Tx prefix hash: 3bebaefb8cda6d00877284dd13281d3a631e7d9784d343523def6ffde1f474b4
Tx public key: 64e9b00b6cc13b3c2299d1a60425d6fbe6099a40e02382fe7e7c8eca70cc7d6f
Timestamp: 1707202112 Timestamp [UCT]: 2024-02-06 06:48:32 Age [y:d:h:m:s]: 00:339:12:13:24
Block: 951448 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 243055 RingCT/type: yes/0
Extra: 0164e9b00b6cc13b3c2299d1a60425d6fbe6099a40e02382fe7e7c8eca70cc7d6f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abf8534d5df52c1ef2c6e1ea80ec950899a948b9d72a871c919b925cc68b2103 0.600000000000 1410214 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": 951458, "vin": [ { "gen": { "height": 951448 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abf8534d5df52c1ef2c6e1ea80ec950899a948b9d72a871c919b925cc68b2103" } } ], "extra": [ 1, 100, 233, 176, 11, 108, 193, 59, 60, 34, 153, 209, 166, 4, 37, 214, 251, 230, 9, 154, 64, 224, 35, 130, 254, 126, 124, 142, 202, 112, 204, 125, 111, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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