Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fe2f03f7842830684ba0b6ce39a86dbdc2efb331d3657e877d2a78d214640bdf

Tx prefix hash: 9732b2e8e51aca271b3fac24aa321bf1d5785243c0fb3290265a54732b675b79
Tx public key: 8f05c8c042ec4f2a2efe4c4af93fd3352595cc2835dbe3855b2feaadb77422f0
Timestamp: 1718273210 Timestamp [UCT]: 2024-06-13 10:06:50 Age [y:d:h:m:s]: 00:226:23:45:05
Block: 1043242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162391 RingCT/type: yes/0
Extra: 018f05c8c042ec4f2a2efe4c4af93fd3352595cc2835dbe3855b2feaadb77422f002110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb9f65dfd8e140b6a7218e684aeb1cd5237d0151f6791623648b2e4d3a15acc2 0.600000000000 1512347 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": 1043252, "vin": [ { "gen": { "height": 1043242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb9f65dfd8e140b6a7218e684aeb1cd5237d0151f6791623648b2e4d3a15acc2" } } ], "extra": [ 1, 143, 5, 200, 192, 66, 236, 79, 42, 46, 254, 76, 74, 249, 63, 211, 53, 37, 149, 204, 40, 53, 219, 227, 133, 91, 47, 234, 173, 183, 116, 34, 240, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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