Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf92fbe3fb83fe62abef74b1e86fbc3ac13075c5206a347d11ca63bdd123ac6c

Tx prefix hash: 09d149c282806995a14c68e0f9395e87bd30bc84c42d64040aec7b75386e28dd
Tx public key: 7ad0d0abc5151a97c93cd4dc79133bc3dcfa361e0a05a9b8c8aec609b40d04b2
Timestamp: 1720539835 Timestamp [UCT]: 2024-07-09 15:43:55 Age [y:d:h:m:s]: 01:127:10:31:55
Block: 1062037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 349603 RingCT/type: yes/0
Extra: 017ad0d0abc5151a97c93cd4dc79133bc3dcfa361e0a05a9b8c8aec609b40d04b202110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89d05ff46bc8421ca38e71c80d596e89a755d8f6348d3ae752943374d70d7d14 0.600000000000 1532538 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": 1062047, "vin": [ { "gen": { "height": 1062037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89d05ff46bc8421ca38e71c80d596e89a755d8f6348d3ae752943374d70d7d14" } } ], "extra": [ 1, 122, 208, 208, 171, 197, 21, 26, 151, 201, 60, 212, 220, 121, 19, 59, 195, 220, 250, 54, 30, 10, 5, 169, 184, 200, 174, 198, 9, 180, 13, 4, 178, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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