Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ba73774479900f2e86ee385b2bb87d8e3e45df16f4e1149d1164b61bca8cff3

Tx prefix hash: c7b37c946343ddc99eb375fc9d7a9386901aaef5cb5c69c10d1d351fcc2515fd
Tx public key: 63fc3ee9f81e3f1b14005028776356828b70df4e5c9b8c6ecc7c2476743474dc
Timestamp: 1730533262 Timestamp [UCT]: 2024-11-02 07:41:02 Age [y:d:h:m:s]: 00:177:18:31:19
Block: 1144792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126924 RingCT/type: yes/0
Extra: 0163fc3ee9f81e3f1b14005028776356828b70df4e5c9b8c6ecc7c2476743474dc0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07541f915da7794bdd0ddd0df374187f4f270910f4a2ef9a83955543696fc897 0.600000000000 1629101 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": 1144802, "vin": [ { "gen": { "height": 1144792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07541f915da7794bdd0ddd0df374187f4f270910f4a2ef9a83955543696fc897" } } ], "extra": [ 1, 99, 252, 62, 233, 248, 30, 63, 27, 20, 0, 80, 40, 119, 99, 86, 130, 139, 112, 223, 78, 92, 155, 140, 110, 204, 124, 36, 118, 116, 52, 116, 220, 2, 17, 0, 0, 0, 4, 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