Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68486be6ba7d56b3f0d169527b9e18b9866035a533f3ecfcdd73c3fa2822fb3e

Tx prefix hash: 51858e602b1bf896b4bc494cf919f4e688050f33a5f95485682a8b21266ab959
Tx public key: b18eb207addf3c16ca7c982f756370e95abfa13c83fff3e7ac67fe852d097eb5
Timestamp: 1707740876 Timestamp [UCT]: 2024-02-12 12:27:56 Age [y:d:h:m:s]: 00:314:08:17:34
Block: 955921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225080 RingCT/type: yes/0
Extra: 01b18eb207addf3c16ca7c982f756370e95abfa13c83fff3e7ac67fe852d097eb50211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6c71c671fce4cb7756e4246ab4c3135c69cd8a1ffd97def64551ed4c142bebe 0.600000000000 1415221 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": 955931, "vin": [ { "gen": { "height": 955921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6c71c671fce4cb7756e4246ab4c3135c69cd8a1ffd97def64551ed4c142bebe" } } ], "extra": [ 1, 177, 142, 178, 7, 173, 223, 60, 22, 202, 124, 152, 47, 117, 99, 112, 233, 90, 191, 161, 60, 131, 255, 243, 231, 172, 103, 254, 133, 45, 9, 126, 181, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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