Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22ad01d355d4e55aeaa2922aeed5ccb8e1c700d9e9bf8d42058b31633a7c698d

Tx prefix hash: 9fad80228828c73df713252c4c007ee7e8d4760c3ab28491516f1e5359b3a73a
Tx public key: 6dc38395df1e77ff795e82cf309e677039dda676ca6a6ff0d2029c8bea3f8b60
Timestamp: 1733506829 Timestamp [UCT]: 2024-12-06 17:40:29 Age [y:d:h:m:s]: 00:157:13:01:42
Block: 1169434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112412 RingCT/type: yes/0
Extra: 016dc38395df1e77ff795e82cf309e677039dda676ca6a6ff0d2029c8bea3f8b600211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2fbfcf167e121240922fead54e385e765e9255087db2aae4a2d5e2835876f8b 0.600000000000 1655151 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": 1169444, "vin": [ { "gen": { "height": 1169434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2fbfcf167e121240922fead54e385e765e9255087db2aae4a2d5e2835876f8b" } } ], "extra": [ 1, 109, 195, 131, 149, 223, 30, 119, 255, 121, 94, 130, 207, 48, 158, 103, 112, 57, 221, 166, 118, 202, 106, 111, 240, 210, 2, 156, 139, 234, 63, 139, 96, 2, 17, 0, 0, 0, 4, 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