Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 849e554d0f4e586656e662d73bcb3d277223602825859d1a06a265904548a33a

Tx prefix hash: 2709f8c74d46cd2911dbf290484e8c5fbe162fc88ba3492e4f868c5c4bf4a798
Tx public key: ea0ef872f88228875519f142e6e526239060cb9d16892a013a7afe68c6f7652a
Timestamp: 1734158258 Timestamp [UCT]: 2024-12-14 06:37:38 Age [y:d:h:m:s]: 00:118:14:37:35
Block: 1174843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84557 RingCT/type: yes/0
Extra: 01ea0ef872f88228875519f142e6e526239060cb9d16892a013a7afe68c6f7652a0211000000111f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73d441a60c93892a379c4ff96c309b8fdc2a841d5981bac99fab3e5fd3c998e3 0.600000000000 1661046 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": 1174853, "vin": [ { "gen": { "height": 1174843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73d441a60c93892a379c4ff96c309b8fdc2a841d5981bac99fab3e5fd3c998e3" } } ], "extra": [ 1, 234, 14, 248, 114, 248, 130, 40, 135, 85, 25, 241, 66, 230, 229, 38, 35, 144, 96, 203, 157, 22, 137, 42, 1, 58, 122, 254, 104, 198, 247, 101, 42, 2, 17, 0, 0, 0, 17, 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