Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2238f9c9dadbe36c987a8b3cc2ec0f1ea693e56cd34eba0ead89081c2890cc5e

Tx prefix hash: 943e491d17ad552604d89e0d046f848327fd49d9920e54d22bac896056f17b5b
Tx public key: 3344a2334f32bde4c8634377f2a72455dbd8180ba6a5d1614ba6c7a943fbae34
Timestamp: 1726203320 Timestamp [UCT]: 2024-09-13 04:55:20 Age [y:d:h:m:s]: 00:282:13:33:39
Block: 1108977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201635 RingCT/type: yes/0
Extra: 013344a2334f32bde4c8634377f2a72455dbd8180ba6a5d1614ba6c7a943fbae34021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5cdfbb40812ce5621334f203065d1babd1040a5dd0567ab8d6d2a43f468a234 0.600000000000 1587066 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": 1108987, "vin": [ { "gen": { "height": 1108977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5cdfbb40812ce5621334f203065d1babd1040a5dd0567ab8d6d2a43f468a234" } } ], "extra": [ 1, 51, 68, 162, 51, 79, 50, 189, 228, 200, 99, 67, 119, 242, 167, 36, 85, 219, 216, 24, 11, 166, 165, 209, 97, 75, 166, 199, 169, 67, 251, 174, 52, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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