Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0759d2f6a0424634d5ce933435010063514ae62e5872b1ccc9dc1bf9eb6e61f2

Tx prefix hash: 120296b6d4705954cb10d4207c871782737d02ae6b2fd0f107c8cd6b9bb3fdae
Tx public key: 2f4b3985cbc1fb7613a735c24102531919b5b300f1632695f7c52a359fb47eb1
Timestamp: 1715347622 Timestamp [UCT]: 2024-05-10 13:27:02 Age [y:d:h:m:s]: 00:325:00:13:38
Block: 1018987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232310 RingCT/type: yes/0
Extra: 012f4b3985cbc1fb7613a735c24102531919b5b300f1632695f7c52a359fb47eb102110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc4f1e4286d855e0672bf18a5f0c9720c1e13d8ae2aa5b6d97938592ca1c6548 0.600000000000 1482832 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": 1018997, "vin": [ { "gen": { "height": 1018987 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc4f1e4286d855e0672bf18a5f0c9720c1e13d8ae2aa5b6d97938592ca1c6548" } } ], "extra": [ 1, 47, 75, 57, 133, 203, 193, 251, 118, 19, 167, 53, 194, 65, 2, 83, 25, 25, 181, 179, 0, 241, 99, 38, 149, 247, 197, 42, 53, 159, 180, 126, 177, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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