Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad35e838031d1e256f3ce931de5b8ec3375e016b0f1a57f03a6949c3c8a06196

Tx prefix hash: 3be5b56e67951259b671a3c0462785705842a07b8b7adfc560f4293921fcb48d
Tx public key: c32810c8e85ea3618ffdd725de6567ae63910c509f49e4a1260e1cc8b005d45a
Timestamp: 1704744572 Timestamp [UCT]: 2024-01-08 20:09:32 Age [y:d:h:m:s]: 01:303:07:23:32
Block: 931067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 475589 RingCT/type: yes/0
Extra: 01c32810c8e85ea3618ffdd725de6567ae63910c509f49e4a1260e1cc8b005d45a02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5663c710bc4d7464513e57f9cb8bd3f293879d97cadcd967a9599af6d2cd6963 0.600000000000 1388959 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": 931077, "vin": [ { "gen": { "height": 931067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5663c710bc4d7464513e57f9cb8bd3f293879d97cadcd967a9599af6d2cd6963" } } ], "extra": [ 1, 195, 40, 16, 200, 232, 94, 163, 97, 143, 253, 215, 37, 222, 101, 103, 174, 99, 145, 12, 80, 159, 73, 228, 161, 38, 14, 28, 200, 176, 5, 212, 90, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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