Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88cf002c65f2eccf62a6a4a8d9908147ec68ab2c6b69a7ca30c159a1b74b9ef7

Tx prefix hash: 0b6578773cf0ec31d98e8be5cfa0afab41301545b57c8a4a709fe6394d6f41c3
Tx public key: 7a0554a2ca68ce62ce5539bbed5e80ecef7215ec27234ccd213cc0be4b89c5f1
Timestamp: 1705891063 Timestamp [UCT]: 2024-01-22 02:37:43 Age [y:d:h:m:s]: 01:080:11:55:09
Block: 940546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318652 RingCT/type: yes/0
Extra: 017a0554a2ca68ce62ce5539bbed5e80ecef7215ec27234ccd213cc0be4b89c5f102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dd0ed509870511d2b29fda6955ddf510d67490e259d5af6c38ee2b421df18c6c 0.600000000000 1398684 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": 940556, "vin": [ { "gen": { "height": 940546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dd0ed509870511d2b29fda6955ddf510d67490e259d5af6c38ee2b421df18c6c" } } ], "extra": [ 1, 122, 5, 84, 162, 202, 104, 206, 98, 206, 85, 57, 187, 237, 94, 128, 236, 239, 114, 21, 236, 39, 35, 76, 205, 33, 60, 192, 190, 75, 137, 197, 241, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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