Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d13c3b097e09c9ed977865cb0c6daeadcc728125d7904c3be23c521ecf16c6e

Tx prefix hash: 4dc6553d07868e3ae38780d8e4b69896018d1eab8d5bf3373db67804660ba792
Tx public key: cef79d50f81efd63188dbb616900cb4053a3aec4c93f19633ca93a85a54b327a
Timestamp: 1657311991 Timestamp [UCT]: 2022-07-08 20:26:31 Age [y:d:h:m:s]: 02:255:18:06:40
Block: 539550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 703939 RingCT/type: yes/0
Extra: 01cef79d50f81efd63188dbb616900cb4053a3aec4c93f19633ca93a85a54b327a0211000000084da16a3a000000000000000000

1 output(s) for total of 10.005689457000 dcy

stealth address amount amount idx
00: 9b1d8b21e58209fb4b460fbb6d04462aeaebecc5d7d23a36865243cba903d672 10.005689457000 969665 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": 539560, "vin": [ { "gen": { "height": 539550 } } ], "vout": [ { "amount": 10005689457, "target": { "key": "9b1d8b21e58209fb4b460fbb6d04462aeaebecc5d7d23a36865243cba903d672" } } ], "extra": [ 1, 206, 247, 157, 80, 248, 30, 253, 99, 24, 141, 187, 97, 105, 0, 203, 64, 83, 163, 174, 196, 201, 63, 25, 99, 60, 169, 58, 133, 165, 75, 50, 122, 2, 17, 0, 0, 0, 8, 77, 161, 106, 58, 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