Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edcfdbbc68872c580c30d6d55e9f0bc852dd455de74c6c9c8db8a1d1db2656a2

Tx prefix hash: 29f257ab6f5c72734d9b4bebceafb473de1870b2e94c4c9c82549424550fc0b3
Tx public key: 782cfb1cfd4a5076f9c2a4a7c04a5f9dc4b233780376bc0f0487c31323a2cc01
Timestamp: 1725315940 Timestamp [UCT]: 2024-09-02 22:25:40 Age [y:d:h:m:s]: 00:213:01:33:23
Block: 1101628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152126 RingCT/type: yes/0
Extra: 01782cfb1cfd4a5076f9c2a4a7c04a5f9dc4b233780376bc0f0487c31323a2cc01021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 84a20b4afbc4d2a6364af1ed0031767af02a5ac91e815a65200c53bbb81f007a 0.600000000000 1577751 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": 1101638, "vin": [ { "gen": { "height": 1101628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84a20b4afbc4d2a6364af1ed0031767af02a5ac91e815a65200c53bbb81f007a" } } ], "extra": [ 1, 120, 44, 251, 28, 253, 74, 80, 118, 249, 194, 164, 167, 192, 74, 95, 157, 196, 178, 51, 120, 3, 118, 188, 15, 4, 135, 195, 19, 35, 162, 204, 1, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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