Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7689f7efd37389382497b1f7d4e02c5e747167f18ab405092b2149726002b753

Tx prefix hash: e3d403c9dfe580bf129ec85c22ae1c145f9edafc40d27772faa71912b64b0167
Tx public key: 60ec1619242a959cf7429f802f66cf5b1164b4686e5c541f4d064f1c9c0d3522
Timestamp: 1736117120 Timestamp [UCT]: 2025-01-05 22:45:20 Age [y:d:h:m:s]: 00:314:13:40:45
Block: 1191043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222329 RingCT/type: yes/0
Extra: 0160ec1619242a959cf7429f802f66cf5b1164b4686e5c541f4d064f1c9c0d352202110000000f1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 907d68566dbbf4bba1df390fce99dff6049b7b2e776ca0d71185bfae095205b6 0.600000000000 1677566 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": 1191053, "vin": [ { "gen": { "height": 1191043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "907d68566dbbf4bba1df390fce99dff6049b7b2e776ca0d71185bfae095205b6" } } ], "extra": [ 1, 96, 236, 22, 25, 36, 42, 149, 156, 247, 66, 159, 128, 47, 102, 207, 91, 17, 100, 180, 104, 110, 92, 84, 31, 77, 6, 79, 28, 156, 13, 53, 34, 2, 17, 0, 0, 0, 15, 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