Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c35e5f574b2a8d02297fc9943f5c678f1c7ae3498a019b3f1246f3fa358c0ee

Tx prefix hash: b2a2b45c3450fb10d063547d776da46d0eebd62ff5906f4e44bd024789023ed1
Tx public key: fa7b9a52a17f67342a7332cb2024bab43249f8ec6607c4bd4ec59b020747d536
Timestamp: 1677622289 Timestamp [UCT]: 2023-02-28 22:11:29 Age [y:d:h:m:s]: 01:240:20:06:57
Block: 707102 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433057 RingCT/type: yes/0
Extra: 01fa7b9a52a17f67342a7332cb2024bab43249f8ec6607c4bd4ec59b020747d536021100000001e6d27f9c000000000000000000

1 output(s) for total of 2.786618044000 dcy

stealth address amount amount idx
00: b48655e0b4c99de8e79d0e50ebe357275b42ca81650846cc4473e17a73d23c22 2.786618044000 1150895 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": 707112, "vin": [ { "gen": { "height": 707102 } } ], "vout": [ { "amount": 2786618044, "target": { "key": "b48655e0b4c99de8e79d0e50ebe357275b42ca81650846cc4473e17a73d23c22" } } ], "extra": [ 1, 250, 123, 154, 82, 161, 127, 103, 52, 42, 115, 50, 203, 32, 36, 186, 180, 50, 73, 248, 236, 102, 7, 196, 189, 78, 197, 155, 2, 7, 71, 213, 54, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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