Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b73f3b2e2834d817d65008e2454bd5325a8b4acadfa9eb91b52eab12a704846

Tx prefix hash: ce75530a4b1487f876e2df90eb9f468acb7443c4c9ccde6b6bb65df0175977df
Tx public key: c47eecda89a1adc765549c61e9b01345bcdf9b18fc1df7172b29b79224e405bc
Timestamp: 1726848831 Timestamp [UCT]: 2024-09-20 16:13:51 Age [y:d:h:m:s]: 00:206:03:11:10
Block: 1114333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147150 RingCT/type: yes/0
Extra: 01c47eecda89a1adc765549c61e9b01345bcdf9b18fc1df7172b29b79224e405bc021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a797751d7fc84168f371be02f8e4b58b0e35ec67348ad4fcb69484011acc3d8 0.600000000000 1594134 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": 1114343, "vin": [ { "gen": { "height": 1114333 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a797751d7fc84168f371be02f8e4b58b0e35ec67348ad4fcb69484011acc3d8" } } ], "extra": [ 1, 196, 126, 236, 218, 137, 161, 173, 199, 101, 84, 156, 97, 233, 176, 19, 69, 188, 223, 155, 24, 252, 29, 247, 23, 43, 41, 183, 146, 36, 228, 5, 188, 2, 17, 0, 0, 0, 2, 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