Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1f70ad0aa89af3f230f186c131df7f5ec765485d38c656a73bf9e468803eeab

Tx prefix hash: 1e44e5c6da4fef97e92d3a17e8d650500e2f9dc2dfcbadc87f81d57215a8b39e
Tx public key: 98f33d09284b13e08c3a69d7d55e3157b8af5b0e1053a3819198998898165294
Timestamp: 1733104260 Timestamp [UCT]: 2024-12-02 01:51:00 Age [y:d:h:m:s]: 00:341:06:06:40
Block: 1166094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241421 RingCT/type: yes/0
Extra: 0198f33d09284b13e08c3a69d7d55e3157b8af5b0e1053a381919899889816529402110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 245ce8417e361c3ed0d0519d32ceb0460d32a3fa7ce0426621d0a4cb5ac2c478 0.600000000000 1651771 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": 1166104, "vin": [ { "gen": { "height": 1166094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "245ce8417e361c3ed0d0519d32ceb0460d32a3fa7ce0426621d0a4cb5ac2c478" } } ], "extra": [ 1, 152, 243, 61, 9, 40, 75, 19, 224, 140, 58, 105, 215, 213, 94, 49, 87, 184, 175, 91, 14, 16, 83, 163, 129, 145, 152, 153, 136, 152, 22, 82, 148, 2, 17, 0, 0, 0, 12, 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