Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a868bfcdd28123a33883551bb4f07952d768d5d5eb1b67dcdc0c152130b11d9

Tx prefix hash: 46a202fcf84af1d09840a538cee1744558994888b692bbe75ecd1fe6fb640f4e
Tx public key: ba9763bd49e2ca0fb6afc6ceeaf0e0f8f4458b4435ede2d9ac04d82abbf516a9
Timestamp: 1720474712 Timestamp [UCT]: 2024-07-08 21:38:32 Age [y:d:h:m:s]: 00:310:19:22:25
Block: 1061503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222084 RingCT/type: yes/0
Extra: 01ba9763bd49e2ca0fb6afc6ceeaf0e0f8f4458b4435ede2d9ac04d82abbf516a9021100000001c26d3a99000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6074ac4351d3a24bf9a470d5b9552c70938fdceaa9b959a548e8f859e3ec1de7 0.600000000000 1531994 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": 1061513, "vin": [ { "gen": { "height": 1061503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6074ac4351d3a24bf9a470d5b9552c70938fdceaa9b959a548e8f859e3ec1de7" } } ], "extra": [ 1, 186, 151, 99, 189, 73, 226, 202, 15, 182, 175, 198, 206, 234, 240, 224, 248, 244, 69, 139, 68, 53, 237, 226, 217, 172, 4, 216, 42, 187, 245, 22, 169, 2, 17, 0, 0, 0, 1, 194, 109, 58, 153, 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