Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fff438bd410299d45306a24639f6b427f1a0547c09737c6ceb982e2d72c2d81

Tx prefix hash: 548f1a18f20b351edcdd248753448237f4ea1da83b9b2bcd2391d8ebfaf1c446
Tx public key: 6ccaae592cc7a31509aa0d80973380cb9bf0de94ccadbc26e280f97d14ac787d
Timestamp: 1729366336 Timestamp [UCT]: 2024-10-19 19:32:16 Age [y:d:h:m:s]: 00:190:04:50:44
Block: 1135203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135733 RingCT/type: yes/0
Extra: 016ccaae592cc7a31509aa0d80973380cb9bf0de94ccadbc26e280f97d14ac787d021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4408e0e1cac58f86e21229f54ef97a4e89fb98fa691caf1d1b2f8dcd05179599 0.600000000000 1618534 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": 1135213, "vin": [ { "gen": { "height": 1135203 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4408e0e1cac58f86e21229f54ef97a4e89fb98fa691caf1d1b2f8dcd05179599" } } ], "extra": [ 1, 108, 202, 174, 89, 44, 199, 163, 21, 9, 170, 13, 128, 151, 51, 128, 203, 155, 240, 222, 148, 204, 173, 188, 38, 226, 128, 249, 125, 20, 172, 120, 125, 2, 17, 0, 0, 0, 4, 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