Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43a5549547595959c5fb057a63ca45198a8e557f3f35e4b4034f9bbae0401951

Tx prefix hash: b2a9c8df036baa379e26b4010c16cb3650e1ae961606c095cc2f7b85629706ab
Tx public key: 4cd4f7baefed5940721cc938fbecf7505b145305d4f6ab512883efcfde7c4802
Timestamp: 1656982603 Timestamp [UCT]: 2022-07-05 00:56:43 Age [y:d:h:m:s]: 03:119:00:41:23
Block: 536805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 864808 RingCT/type: yes/0
Extra: 014cd4f7baefed5940721cc938fbecf7505b145305d4f6ab512883efcfde7c480202110000000175e3f0e9000000000000000000

1 output(s) for total of 10.217445933000 dcy

stealth address amount amount idx
00: df0c55989ec2bbc23bd201f9e6b3a80b5613269c05aff30bcca9966b09f3acf2 10.217445933000 966608 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": 536815, "vin": [ { "gen": { "height": 536805 } } ], "vout": [ { "amount": 10217445933, "target": { "key": "df0c55989ec2bbc23bd201f9e6b3a80b5613269c05aff30bcca9966b09f3acf2" } } ], "extra": [ 1, 76, 212, 247, 186, 239, 237, 89, 64, 114, 28, 201, 56, 251, 236, 247, 80, 91, 20, 83, 5, 212, 246, 171, 81, 40, 131, 239, 207, 222, 124, 72, 2, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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