Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01adb648b5784ee126d84cae0f27cd47a89a431500d5a12bdb9e63fed90a382f

Tx prefix hash: 574f5ae205adf06991c9904fdd94f3e3d87442fbee6636497035215153ba10ea
Tx public key: fb18adbaf2851ad657eac3cb0f69ea8e77da1bb0a915b2afff71a927376878c8
Timestamp: 1672812249 Timestamp [UCT]: 2023-01-04 06:04:09 Age [y:d:h:m:s]: 01:333:02:44:48
Block: 667218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499087 RingCT/type: yes/0
Extra: 01fb18adbaf2851ad657eac3cb0f69ea8e77da1bb0a915b2afff71a927376878c802110000000352542ceb000000000000000000

1 output(s) for total of 3.777719883000 dcy

stealth address amount amount idx
00: c11b36786aca307fb8b287ead7ee66f58f7680fa2a4b593b1e80b29494b3c948 3.777719883000 1108385 of 0

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": 667228, "vin": [ { "gen": { "height": 667218 } } ], "vout": [ { "amount": 3777719883, "target": { "key": "c11b36786aca307fb8b287ead7ee66f58f7680fa2a4b593b1e80b29494b3c948" } } ], "extra": [ 1, 251, 24, 173, 186, 242, 133, 26, 214, 87, 234, 195, 203, 15, 105, 234, 142, 119, 218, 27, 176, 169, 21, 178, 175, 255, 113, 169, 39, 55, 104, 120, 200, 2, 17, 0, 0, 0, 3, 82, 84, 44, 235, 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