Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 92255876a52d4dace747485f21f3e0350ccf3f4c56ad0f5783ccb0c98ce1832d

Tx prefix hash: e9bae197fdd55d74bee24a3bfd994bd96a353207d0c908649db061cd9c805767
Tx public key: 3fddc7dbfaada52248bbc0f4bb7aa612ff4bb1df1efed822f14391dde16e1b79
Timestamp: 1732100703 Timestamp [UCT]: 2024-11-20 11:05:03 Age [y:d:h:m:s]: 00:149:03:51:49
Block: 1157773 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106444 RingCT/type: yes/0
Extra: 013fddc7dbfaada52248bbc0f4bb7aa612ff4bb1df1efed822f14391dde16e1b790211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 260ddd0c95ce8db9ee4afc5783db5a7fc37a14a0ae77cf90e16e50a57fd3e861 0.600000000000 1643396 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": 1157783, "vin": [ { "gen": { "height": 1157773 } } ], "vout": [ { "amount": 600000000, "target": { "key": "260ddd0c95ce8db9ee4afc5783db5a7fc37a14a0ae77cf90e16e50a57fd3e861" } } ], "extra": [ 1, 63, 221, 199, 219, 250, 173, 165, 34, 72, 187, 192, 244, 187, 122, 166, 18, 255, 75, 177, 223, 30, 254, 216, 34, 241, 67, 145, 221, 225, 110, 27, 121, 2, 17, 0, 0, 0, 3, 31, 10, 83, 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