Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91ec467be5e7d3abf89b0a7ffa347ac16002f82936efeef447680a59c6d4d547

Tx prefix hash: 8331d6a8a9b4d022844c7b658ad0df1129f88a865f046d4589b178f201875aa1
Tx public key: 784d817d6a18f19b0261570a8daf229da695f9cb88cd7518f0de32ed792c5389
Timestamp: 1712859794 Timestamp [UCT]: 2024-04-11 18:23:14 Age [y:d:h:m:s]: 01:064:18:28:14
Block: 998336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307205 RingCT/type: yes/0
Extra: 01784d817d6a18f19b0261570a8daf229da695f9cb88cd7518f0de32ed792c538902110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a98a7c4d5248c8fccd90ea0b4ead3cdb40889e97a5dd86b40f253ca4d88bd874 0.600000000000 1458782 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": 998346, "vin": [ { "gen": { "height": 998336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a98a7c4d5248c8fccd90ea0b4ead3cdb40889e97a5dd86b40f253ca4d88bd874" } } ], "extra": [ 1, 120, 77, 129, 125, 106, 24, 241, 155, 2, 97, 87, 10, 141, 175, 34, 157, 166, 149, 249, 203, 136, 205, 117, 24, 240, 222, 50, 237, 121, 44, 83, 137, 2, 17, 0, 0, 0, 10, 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