Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 662835d28adebc6f4cfa0be5d4c261e4057cc210be4e1f4635bedb5f13a5ce70

Tx prefix hash: 182d2d2f84384d9c35f2a41eb12e5024e6d09708c7a4cf1c71c3498e5d977cde
Tx public key: 593721a587fedd5ba1a8f8a9970f426f83ae0262d3ec3461d5441d6c1e2e8d09
Timestamp: 1697399918 Timestamp [UCT]: 2023-10-15 19:58:38 Age [y:d:h:m:s]: 01:358:23:08:58
Block: 870387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 515259 RingCT/type: yes/0
Extra: 01593721a587fedd5ba1a8f8a9970f426f83ae0262d3ec3461d5441d6c1e2e8d09021100000001faf35c9c000000000000000000

1 output(s) for total of 0.801764053000 dcy

stealth address amount amount idx
00: a61629b83b1c9112767395642f7a7b9fe1f23fb7fd3b054322caaee11cafcc21 0.801764053000 1325266 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": 870397, "vin": [ { "gen": { "height": 870387 } } ], "vout": [ { "amount": 801764053, "target": { "key": "a61629b83b1c9112767395642f7a7b9fe1f23fb7fd3b054322caaee11cafcc21" } } ], "extra": [ 1, 89, 55, 33, 165, 135, 254, 221, 91, 161, 168, 248, 169, 151, 15, 66, 111, 131, 174, 2, 98, 211, 236, 52, 97, 213, 68, 29, 108, 30, 46, 141, 9, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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