Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c407e0a8812197c0307cf64fc6f3282f5bba5d9764f0d6b363c5eb4dc297e519

Tx prefix hash: 95137c2eba3bc448b59e925a71b0c827529cbdcbdd14eb380746d42e41b8d507
Tx public key: 224906c6d3b6f8ad61b6e01478155c7f95971694aa320baeaf7d73c3e81b3004
Timestamp: 1740891565 Timestamp [UCT]: 2025-03-02 04:59:25 Age [y:d:h:m:s]: 00:263:03:02:04
Block: 1230287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185820 RingCT/type: yes/0
Extra: 01224906c6d3b6f8ad61b6e01478155c7f95971694aa320baeaf7d73c3e81b3004021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6841e1bbbe83854218c2c7ca8fb26e9c6df4515e588ac85b5c80ab9412532a41 0.600000000000 1717184 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": 1230297, "vin": [ { "gen": { "height": 1230287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6841e1bbbe83854218c2c7ca8fb26e9c6df4515e588ac85b5c80ab9412532a41" } } ], "extra": [ 1, 34, 73, 6, 198, 211, 182, 248, 173, 97, 182, 224, 20, 120, 21, 92, 127, 149, 151, 22, 148, 170, 50, 11, 174, 175, 125, 115, 195, 232, 27, 48, 4, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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