Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03bd55810b998d2feafd6278cf7993b18b1a904dcf3f79d3897534b823fe8804

Tx prefix hash: 8d149e289e909d9252a1734bef5a45c1c70006c1e4055af3d5b7ccb9aa0d509a
Tx public key: 7cd761f0d67f30e2f67dd4b9b569a56aaba68fba06e984d7c10ddccdb38d7750
Timestamp: 1728697606 Timestamp [UCT]: 2024-10-12 01:46:46 Age [y:d:h:m:s]: 00:165:11:55:06
Block: 1129670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118046 RingCT/type: yes/0
Extra: 017cd761f0d67f30e2f67dd4b9b569a56aaba68fba06e984d7c10ddccdb38d77500211000000013cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20b5efb121abd92010fa6a8234054bab001d7d5db265b6054b808596f3b7bd7c 0.600000000000 1612503 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": 1129680, "vin": [ { "gen": { "height": 1129670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20b5efb121abd92010fa6a8234054bab001d7d5db265b6054b808596f3b7bd7c" } } ], "extra": [ 1, 124, 215, 97, 240, 214, 127, 48, 226, 246, 125, 212, 185, 181, 105, 165, 106, 171, 166, 143, 186, 6, 233, 132, 215, 193, 13, 220, 205, 179, 141, 119, 80, 2, 17, 0, 0, 0, 1, 60, 208, 252, 6, 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