Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b90097b051192658964a54ec4e96bc1c7555ce13cf86969dccc3ad634e0b9927

Tx prefix hash: 597dac498bf2b0a52da9c2d188d71579f1c1a7d3e621fa2c67abfc13ac48c62c
Tx public key: fad5e5c34c1c60540ea5c072616b70d1c1aae56950281c737f426b7d114ffa20
Timestamp: 1718566847 Timestamp [UCT]: 2024-06-16 19:40:47 Age [y:d:h:m:s]: 00:276:02:32:19
Block: 1045688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197307 RingCT/type: yes/0
Extra: 01fad5e5c34c1c60540ea5c072616b70d1c1aae56950281c737f426b7d114ffa200211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cdae34910defd291baa7cb17e9815f3bc0eb5ce5af7d2f1c719d46a1a6d806b2 0.600000000000 1515327 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": 1045698, "vin": [ { "gen": { "height": 1045688 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cdae34910defd291baa7cb17e9815f3bc0eb5ce5af7d2f1c719d46a1a6d806b2" } } ], "extra": [ 1, 250, 213, 229, 195, 76, 28, 96, 84, 14, 165, 192, 114, 97, 107, 112, 209, 193, 170, 229, 105, 80, 40, 28, 115, 127, 66, 107, 125, 17, 79, 250, 32, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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