Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68585012bb573a8c5a57cbb652cf77696a98a7a0df9d519e10d332558356ce03

Tx prefix hash: 9b7281c6bbe8cbd8dd07498aea563f5be85f50c726b8b948fc20d92a6ea3fbcd
Tx public key: ba83866be5d6229d78082bd0882d85c20beca61f7c16d9dccde7b7b0f9b119bc
Timestamp: 1719522124 Timestamp [UCT]: 2024-06-27 21:02:04 Age [y:d:h:m:s]: 00:273:06:22:30
Block: 1053589 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195249 RingCT/type: yes/0
Extra: 01ba83866be5d6229d78082bd0882d85c20beca61f7c16d9dccde7b7b0f9b119bc0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de806317f82b3f333c5e1564e28badb916c0fa6f4931fa1c1db7af0d02a5fb0e 0.600000000000 1523936 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": 1053599, "vin": [ { "gen": { "height": 1053589 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de806317f82b3f333c5e1564e28badb916c0fa6f4931fa1c1db7af0d02a5fb0e" } } ], "extra": [ 1, 186, 131, 134, 107, 229, 214, 34, 157, 120, 8, 43, 208, 136, 45, 133, 194, 11, 236, 166, 31, 124, 22, 217, 220, 205, 231, 183, 176, 249, 177, 25, 188, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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