Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a44ec1baad6099eed830d0a167d1c55baa1150b6675eee3a2a19b0accb7f2efd

Tx prefix hash: a5ff95dcf3582752154f74f4332803db0f8cfedec2afeb472e6671e655a927aa
Tx public key: b340c3ad5fc3b7cdab522ce60c27251a87d81ac510d736abe74eaca807bf1b6f
Timestamp: 1728922428 Timestamp [UCT]: 2024-10-14 16:13:48 Age [y:d:h:m:s]: 00:176:08:30:28
Block: 1131531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125817 RingCT/type: yes/0
Extra: 01b340c3ad5fc3b7cdab522ce60c27251a87d81ac510d736abe74eaca807bf1b6f021100000001578df8ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f565bffa7affbecf7a3c0fb5d91ccc1c4c275d922a80eba59849bb42d681bde1 0.600000000000 1614434 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": 1131541, "vin": [ { "gen": { "height": 1131531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f565bffa7affbecf7a3c0fb5d91ccc1c4c275d922a80eba59849bb42d681bde1" } } ], "extra": [ 1, 179, 64, 195, 173, 95, 195, 183, 205, 171, 82, 44, 230, 12, 39, 37, 26, 135, 216, 26, 197, 16, 215, 54, 171, 231, 78, 172, 168, 7, 191, 27, 111, 2, 17, 0, 0, 0, 1, 87, 141, 248, 172, 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