Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e32083ce8ed658f5f233ec9ca987d5f54bb72987b75e5690ba1c06ab7e36b672

Tx prefix hash: 693f96e7891c332d1ff769099d28eaf1f628ad4f3777773867ab62ab3e447cb0
Tx public key: 7f70eabb14e6753b98ecde55a908699d819ddbcd60b6c93e15b74ea5d085bdd5
Timestamp: 1725594907 Timestamp [UCT]: 2024-09-06 03:55:07 Age [y:d:h:m:s]: 00:204:02:06:14
Block: 1103937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145704 RingCT/type: yes/0
Extra: 017f70eabb14e6753b98ecde55a908699d819ddbcd60b6c93e15b74ea5d085bdd5021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1849fe7ea52954b3690bcf9ec6028c4e6a6458e9375e2429b822d777e04033e8 0.600000000000 1580960 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": 1103947, "vin": [ { "gen": { "height": 1103937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1849fe7ea52954b3690bcf9ec6028c4e6a6458e9375e2429b822d777e04033e8" } } ], "extra": [ 1, 127, 112, 234, 187, 20, 230, 117, 59, 152, 236, 222, 85, 169, 8, 105, 157, 129, 157, 219, 205, 96, 182, 201, 62, 21, 183, 78, 165, 208, 133, 189, 213, 2, 17, 0, 0, 0, 4, 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