Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f087499b245f06d4c869f3c4b50cf97da413faf2cd99663c65d7739a217972d4

Tx prefix hash: ada493945cd68543aaf42719c62fa6322e17230c321ac9743dfb6f94e134c82b
Tx public key: db4c3014d9e1c0dffe393df804ca68ceb28471eb3785c48ca5a582f92e9a1884
Timestamp: 1632810874 Timestamp [UCT]: 2021-09-28 06:34:34 Age [y:d:h:m:s]: 03:163:10:37:14
Block: 342330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 893349 RingCT/type: yes/0
Extra: 01db4c3014d9e1c0dffe393df804ca68ceb28471eb3785c48ca5a582f92e9a1884021100000025fdc024ec000000000000000000

1 output(s) for total of 45.054534318000 dcy

stealth address amount amount idx
00: a1f4bc6369375b6b9cf73c382060e7e15e4e2288c0f31919c2ba859119b2350b 45.054534318000 703010 of 0

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": 342340, "vin": [ { "gen": { "height": 342330 } } ], "vout": [ { "amount": 45054534318, "target": { "key": "a1f4bc6369375b6b9cf73c382060e7e15e4e2288c0f31919c2ba859119b2350b" } } ], "extra": [ 1, 219, 76, 48, 20, 217, 225, 192, 223, 254, 57, 61, 248, 4, 202, 104, 206, 178, 132, 113, 235, 55, 133, 196, 140, 165, 165, 130, 249, 46, 154, 24, 132, 2, 17, 0, 0, 0, 37, 253, 192, 36, 236, 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