Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b574020f7447605cc108e1cc254ac1b697c9185d20f08d027c249623e8d1a4f

Tx prefix hash: 738b0e227c6e69374e20687b13fdb6505caa9b024a06eae2c654a470aeb2d5ac
Tx public key: d1ec81f7d702823b82168117c4e304579b212ea0e8e1a2138166cd24b4c922a3
Timestamp: 1732126556 Timestamp [UCT]: 2024-11-20 18:15:56 Age [y:d:h:m:s]: 00:134:17:04:14
Block: 1157992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96096 RingCT/type: yes/0
Extra: 01d1ec81f7d702823b82168117c4e304579b212ea0e8e1a2138166cd24b4c922a30211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21715875643ce5f48eecd26017839714025a59399195c4a808299d8ec9d5edcc 0.600000000000 1643615 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": 1158002, "vin": [ { "gen": { "height": 1157992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21715875643ce5f48eecd26017839714025a59399195c4a808299d8ec9d5edcc" } } ], "extra": [ 1, 209, 236, 129, 247, 215, 2, 130, 59, 130, 22, 129, 23, 196, 227, 4, 87, 155, 33, 46, 160, 232, 225, 162, 19, 129, 102, 205, 36, 180, 201, 34, 163, 2, 17, 0, 0, 0, 2, 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