Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e747d0087a0a239006a76f9ad85e3fa1e4cc3e66241dea56c73ef4dda147e4b

Tx prefix hash: 1a36e4e8db16cb08bcdefc2b2b461d124640b4d6988b57cd8c32657373f21676
Tx public key: 6ae01fc73367b885b15f5883b0f0e72801e3a9ee44dac8c953e36872d9d2e39a
Timestamp: 1735518794 Timestamp [UCT]: 2024-12-30 00:33:14 Age [y:d:h:m:s]: 00:101:08:30:02
Block: 1186081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72231 RingCT/type: yes/0
Extra: 016ae01fc73367b885b15f5883b0f0e72801e3a9ee44dac8c953e36872d9d2e39a0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7278aecedaab6eaf7c2f7ea82c1e68f231ea9e8eb5c2edeff3034f6486b08f7 0.600000000000 1672556 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": 1186091, "vin": [ { "gen": { "height": 1186081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7278aecedaab6eaf7c2f7ea82c1e68f231ea9e8eb5c2edeff3034f6486b08f7" } } ], "extra": [ 1, 106, 224, 31, 199, 51, 103, 184, 133, 177, 95, 88, 131, 176, 240, 231, 40, 1, 227, 169, 238, 68, 218, 200, 201, 83, 227, 104, 114, 217, 210, 227, 154, 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