Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6b0317bed87565c009f5c33d89619009488b56db863aee5ec38cb79bd52fc76

Tx prefix hash: c70e8ee7f512b14401d9fd124e9f547468e47ec7f147b4d3e4b1be8e292d4160
Tx public key: c90cbd118274f79c9d5a8f705160d73b8ec8835897f5f00cd0dcb6d38a13af70
Timestamp: 1731807867 Timestamp [UCT]: 2024-11-17 01:44:27 Age [y:d:h:m:s]: 00:210:17:01:57
Block: 1155344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150376 RingCT/type: yes/0
Extra: 01c90cbd118274f79c9d5a8f705160d73b8ec8835897f5f00cd0dcb6d38a13af70021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5554fea0456f9cb537f22bccbf9005116cf60cd99b6f4f61225b50b25a97a0c8 0.600000000000 1640959 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": 1155354, "vin": [ { "gen": { "height": 1155344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5554fea0456f9cb537f22bccbf9005116cf60cd99b6f4f61225b50b25a97a0c8" } } ], "extra": [ 1, 201, 12, 189, 17, 130, 116, 247, 156, 157, 90, 143, 112, 81, 96, 215, 59, 142, 200, 131, 88, 151, 245, 240, 12, 208, 220, 182, 211, 138, 19, 175, 112, 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