Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9fdec99635cb399182f4bf084869ff0c4be83ad597884404f17352b943defa6d

Tx prefix hash: e7bef2a6afbc7c73265f1278ae17fe531012877f9d118fbdd48f35589a90828b
Tx public key: e1b6ce11e779ec08d6601b8183e6aa832e7c6989c1e320f514bc1f914f0b5730
Timestamp: 1725574105 Timestamp [UCT]: 2024-09-05 22:08:25 Age [y:d:h:m:s]: 00:079:17:23:58
Block: 1103773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57015 RingCT/type: yes/0
Extra: 01e1b6ce11e779ec08d6601b8183e6aa832e7c6989c1e320f514bc1f914f0b5730021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4edb372db2af83d6d25a59900732bd3c39cb39504fafdcfd004e846d54562b9 0.600000000000 1580730 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": 1103783, "vin": [ { "gen": { "height": 1103773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4edb372db2af83d6d25a59900732bd3c39cb39504fafdcfd004e846d54562b9" } } ], "extra": [ 1, 225, 182, 206, 17, 231, 121, 236, 8, 214, 96, 27, 129, 131, 230, 170, 131, 46, 124, 105, 137, 193, 227, 32, 245, 20, 188, 31, 145, 79, 11, 87, 48, 2, 17, 0, 0, 0, 2, 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