Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee938c3005f0661deeed09caeceb6ed213917c56440f7660468d8b5dcaf1ebeb

Tx prefix hash: 075c079b59c2d0d7651453c50aea0d15c10accf8692eab5c69ce94ef47c5a530
Tx public key: fd1e9320ec431d84d7d2e51e45dd0badf2bc5d3caa919c231cd148037430cd81
Timestamp: 1733121919 Timestamp [UCT]: 2024-12-02 06:45:19 Age [y:d:h:m:s]: 00:121:22:21:21
Block: 1166245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86932 RingCT/type: yes/0
Extra: 01fd1e9320ec431d84d7d2e51e45dd0badf2bc5d3caa919c231cd148037430cd81021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c5a17fca3f10fd6a033535c64edd11ada3d08461cb79b4283620c8c9585645a 0.600000000000 1651922 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": 1166255, "vin": [ { "gen": { "height": 1166245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c5a17fca3f10fd6a033535c64edd11ada3d08461cb79b4283620c8c9585645a" } } ], "extra": [ 1, 253, 30, 147, 32, 236, 67, 29, 132, 215, 210, 229, 30, 69, 221, 11, 173, 242, 188, 93, 60, 170, 145, 156, 35, 28, 209, 72, 3, 116, 48, 205, 129, 2, 17, 0, 0, 0, 1, 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