Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4c56ec6cc2cf2c36ad236b5ccc51b562fbcb21fb25c3ce7667eb9f863403de4

Tx prefix hash: c115797055415038502b1fe70fd24d0e5a3d40163f32a4437eb816cb46d1a7c4
Tx public key: c6e0a42f70cceedae9147cbc349feffeff173e6a0d9a9d44e19f4a41bee3b637
Timestamp: 1763424210 Timestamp [UCT]: 2025-11-18 00:03:30 Age [y:d:h:m:s]: 00:041:01:01:24
Block: 1414438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29383 RingCT/type: yes/0
Extra: 01c6e0a42f70cceedae9147cbc349feffeff173e6a0d9a9d44e19f4a41bee3b6370211000000018ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55f7f2cf45e2f21d126b5871878246658fee0dca4e39086097dcaf854c0ce35d 0.600000000000 1902927 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": 1414448, "vin": [ { "gen": { "height": 1414438 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55f7f2cf45e2f21d126b5871878246658fee0dca4e39086097dcaf854c0ce35d" } } ], "extra": [ 1, 198, 224, 164, 47, 112, 204, 238, 218, 233, 20, 124, 188, 52, 159, 239, 254, 255, 23, 62, 106, 13, 154, 157, 68, 225, 159, 74, 65, 190, 227, 182, 55, 2, 17, 0, 0, 0, 1, 140, 235, 127, 9, 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