Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4f48916669de7147741b73511c00a3324b827fe1d341be219c31871e77b9e6a

Tx prefix hash: 7fae75c2e912234ce88b4d7239a3da9b89971e7512539919b1f8137188742def
Tx public key: 2a574b44670e9ab047341ca1d9032b81cb8947dd9af207f4601f1b4fee855545
Timestamp: 1736343725 Timestamp [UCT]: 2025-01-08 13:42:05 Age [y:d:h:m:s]: 00:076:10:54:25
Block: 1192915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54403 RingCT/type: yes/0
Extra: 012a574b44670e9ab047341ca1d9032b81cb8947dd9af207f4601f1b4fee8555450211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45589f62a4b5c1da922db0bf5e31c39e36f18a72b440aeaa6a65f13b0669f0b0 0.600000000000 1679472 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": 1192925, "vin": [ { "gen": { "height": 1192915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45589f62a4b5c1da922db0bf5e31c39e36f18a72b440aeaa6a65f13b0669f0b0" } } ], "extra": [ 1, 42, 87, 75, 68, 103, 14, 154, 176, 71, 52, 28, 161, 217, 3, 43, 129, 203, 137, 71, 221, 154, 242, 7, 244, 96, 31, 27, 79, 238, 133, 85, 69, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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