Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49656c319241616ba1657e436f110ed7cae1529b4a45b5e7366436916e2f099c

Tx prefix hash: a80492103ea45f155746eb41aa7ae189ac6ae4faf3a43325644382cca31d78f9
Tx public key: 5c58e9f9a681eff546f2756743767541ebc9fb78ad77f4a0a47a8e69d241d4b9
Timestamp: 1733251518 Timestamp [UCT]: 2024-12-03 18:45:18 Age [y:d:h:m:s]: 00:193:17:53:52
Block: 1167317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 138216 RingCT/type: yes/0
Extra: 015c58e9f9a681eff546f2756743767541ebc9fb78ad77f4a0a47a8e69d241d4b9021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea4e1dd477de8dc01c895f8d330b6cf7b4dcbe777a4caf26032b944b82493eac 0.600000000000 1653012 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": 1167327, "vin": [ { "gen": { "height": 1167317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea4e1dd477de8dc01c895f8d330b6cf7b4dcbe777a4caf26032b944b82493eac" } } ], "extra": [ 1, 92, 88, 233, 249, 166, 129, 239, 245, 70, 242, 117, 103, 67, 118, 117, 65, 235, 201, 251, 120, 173, 119, 244, 160, 164, 122, 142, 105, 210, 65, 212, 185, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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