Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4e9b34ecef8d5d0f1491ffa6f667c35abe5c55e3131d93d82a35ac91608d93a

Tx prefix hash: bc9ca3805e456d8c6a6428cc3900e28144e9e8d5193601184de4929a08e5dae4
Tx public key: d85c1e6a4d2a1c148663bf34da402c0c293319133931f3dfe6e17c9c38821a60
Timestamp: 1759391151 Timestamp [UCT]: 2025-10-02 07:45:51 Age [y:d:h:m:s]: 00:005:15:01:58
Block: 1381009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4020 RingCT/type: yes/0
Extra: 01d85c1e6a4d2a1c148663bf34da402c0c293319133931f3dfe6e17c9c38821a60021100000001a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40f4d9be20a016e710f040f900c1ba4b355000c4624792396efc88c4d2e07765 0.600000000000 1869120 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": 1381019, "vin": [ { "gen": { "height": 1381009 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40f4d9be20a016e710f040f900c1ba4b355000c4624792396efc88c4d2e07765" } } ], "extra": [ 1, 216, 92, 30, 106, 77, 42, 28, 20, 134, 99, 191, 52, 218, 64, 44, 12, 41, 51, 25, 19, 57, 49, 243, 223, 230, 225, 124, 156, 56, 130, 26, 96, 2, 17, 0, 0, 0, 1, 165, 220, 205, 121, 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