Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 268ba1e447d8dbae732d7c61e0b6ce8a930348f1045bce86b63d878967bd8e7c

Tx prefix hash: 441ec5d9ac88bd752bbd29503f550d44c8fee1632782487ee23cac533f039544
Tx public key: d139f88ff27cd5cec8328c127bd2a69cf573c5fe344f08cf77cd21d4b8a6f2c7
Timestamp: 1732966023 Timestamp [UCT]: 2024-11-30 11:27:03 Age [y:d:h:m:s]: 00:118:12:51:58
Block: 1164956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84520 RingCT/type: yes/0
Extra: 01d139f88ff27cd5cec8328c127bd2a69cf573c5fe344f08cf77cd21d4b8a6f2c70211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28b249b9ff8f4c6bd29bfa8fafaa0ae2ae67ad1ea0874f4e39c21a61ef1cbdef 0.600000000000 1650631 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": 1164966, "vin": [ { "gen": { "height": 1164956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28b249b9ff8f4c6bd29bfa8fafaa0ae2ae67ad1ea0874f4e39c21a61ef1cbdef" } } ], "extra": [ 1, 209, 57, 248, 143, 242, 124, 213, 206, 200, 50, 140, 18, 123, 210, 166, 156, 245, 115, 197, 254, 52, 79, 8, 207, 119, 205, 33, 212, 184, 166, 242, 199, 2, 17, 0, 0, 0, 2, 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