Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e6fbaa3f46d2ed4eecd1a54b7257f3eabd5868946b9af2691afa1e1e1c9c913

Tx prefix hash: 836f9327b64ff1edef69414d57fc20ab161c10699bee96a1419f6f0f1050c22d
Tx public key: 994c13b8bdec60bfa63abf0fe84327504e2049121f294312f89ad158e1d4bacb
Timestamp: 1735460158 Timestamp [UCT]: 2024-12-29 08:15:58 Age [y:d:h:m:s]: 00:097:03:38:38
Block: 1185595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69237 RingCT/type: yes/0
Extra: 01994c13b8bdec60bfa63abf0fe84327504e2049121f294312f89ad158e1d4bacb021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0672edaba6a067b422c56e2f805301a64c13f4a4c706415c697071b2aa6a93b 0.600000000000 1672070 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": 1185605, "vin": [ { "gen": { "height": 1185595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0672edaba6a067b422c56e2f805301a64c13f4a4c706415c697071b2aa6a93b" } } ], "extra": [ 1, 153, 76, 19, 184, 189, 236, 96, 191, 166, 58, 191, 15, 232, 67, 39, 80, 78, 32, 73, 18, 31, 41, 67, 18, 248, 154, 209, 88, 225, 212, 186, 203, 2, 17, 0, 0, 0, 5, 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